feat(panel): LLM feedback panel that drives the app and reports UX gaps - #201
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An automated, reproducible way to get outside-eyes UX feedback: a panel of different vendors' vision LLMs each drive a real browser to organize a project, then give structured product feedback we can act on. It's the "measure vs Asana" design loop, automated.
How it works
AWS_PROFILE=personal, us-west-2 — no API keys, no SDK dep): Anthropic Claude Haiku 4.5, Amazon Nova Pro, Meta Llama 4 Maverick, Mistral Pixtral Large.click/type/enter/goto/note/doneby element number, not pixel coords — robust across vendors) → Playwright executes it → repeat (step cap 22).report.mdwith a score table and improvement themes ranked by how many panelists raised each.Run it
Scenarios:
wedding(default — a couple planning their wedding, per the idea),launch,trip. Output →/tmp/tf-panel/<PANEL_RUN_ID>/.First real signal (smoke run, Claude Haiku, wedding)
Delight 2/10 — "felt broken; no confirmation after creating a project; had to retry." Actionable backlog it surfaced: success toast / optimistic insert / loading state on project + task creation. (Partly the model wrestling with the create-form flow, partly a genuine lack of success feedback — worth fixing either way.)
Scope / gates
scripts/llm-panel/— a harness, exempt from the line/CRAP gate (notsrc/amplify); eslint doesn't lint those.mjs. No app code touched, so coverage/CRAP are unaffected.CLAUDE.md→ Design → LLM feedback panel (incl. the inference-profile model-id gotcha).Full quality gate green.